home *** CD-ROM | disk | FTP | other *** search
ggggeeeettttttttyyyyddddeeeeffffssss((((4444)))) ggggeeeettttttttyyyyddddeeeeffffssss((((4444)))) NNNNAAAAMMMMEEEE gettydefs - speed and terminal settings used by getty DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The /_e_t_c/_g_e_t_t_y_d_e_f_s file contains information used by _g_e_t_t_y(1M) to set up the speed and terminal settings for a line. It supplies information on what the _l_o_g_i_n(1) prompt should look like. It also supplies the speed to try next if the user indicates the current speed is not correct by typing a <<<<bbbbrrrreeeeaaaakkkk>>>> character. NNNNooootttteeee:::: Customers who need to support terminals that pass 8 bits to the system (as is typical outside the U.S.) must modify the entries in /_e_t_c/_g_e_t_t_y_d_e_f_s as described in the WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS section. Each entry in /_e_t_c/_g_e_t_t_y_d_e_f_s has the following format: label# initial-flags # final-flags # login-prompt #next-label Each entry is followed by a blank line. The various fields can contain quoted characters of the form \\\\bbbb, \\\\nnnn, \\\\cccc, and so on as well as \\\\_n_n_n, where _n_n_n is the octal value of the desired character. The various fields are: _l_a_b_e_l This is the string against which _g_e_t_t_y tries to match its second argument. It is often the speed, such as 1111222200000000, at which the terminal is supposed to run, but it need not be (see below). _i_n_i_t_i_a_l-_f_l_a_g_s These flags are the initial _i_o_c_t_l(2) settings to which the terminal is to be set if a terminal type is not specified to _g_e_t_t_y. The flags that _g_e_t_t_y understands are the same as the ones listed in /_u_s_r/_i_n_c_l_u_d_e/_s_y_s/_t_e_r_m_i_o._h (see _t_e_r_m_i_o(7)). Normally only the speed flag is required in the _i_n_i_t_i_a_l-_f_l_a_g_s. _g_e_t_t_y automatically sets the terminal to raw input mode and takes care of most of the other flags. The _i_n_i_t_i_a_l-_f_l_a_g settings remain in effect until _g_e_t_t_y executes _l_o_g_i_n. _f_i_n_a_l-_f_l_a_g_s These flags take the same values as the _i_n_i_t_i_a_l-_f_l_a_g_s and are set just before _g_e_t_t_y executes _l_o_g_i_n. The speed flag is again required. The composite flag SSSSAAAANNNNEEEE takes care of most of the other flags that need to be set so that the processor and terminal are communicating in a rational fashion. The other two commonly specified _f_i_n_a_l-_f_l_a_g_s are TTTTAAAABBBB3333, so that tabs are sent to the terminal as spaces, and HHHHUUUUPPPPCCCCLLLL, so that the line is hung up on the final close. _l_o_g_i_n-_p_r_o_m_p_t This entire field is printed as the _l_o_g_i_n-_p_r_o_m_p_t. Unlike the above fields where white space is ignored (a space, tab, or newline), they are included in the _l_o_g_i_n-_p_r_o_m_p_t field. As a special feature, this field can contain the string $$$$HHHHOOOOSSSSTTTTNNNNAAAAMMMMEEEE, which is replaced by the current PPPPaaaaggggeeee 1111 ggggeeeettttttttyyyyddddeeeeffffssss((((4444)))) ggggeeeettttttttyyyyddddeeeeffffssss((((4444)))) hostname of the machine. See _h_o_s_t_n_a_m_e(1) for more information. _n_e_x_t-_l_a_b_e_l If this entry does not specify the desired speed, indicated by the user typing a <<<<bbbbrrrreeeeaaaakkkk>>>> character, then _g_e_t_t_y searches for the entry with _n_e_x_t-_l_a_b_e_l as its _l_a_b_e_l field and sets up the terminal for those settings. Usually, a series of speeds are linked together in this fashion, into a closed set; for instance, 2222444400000000 linked to 1111222200000000, which is linked to 333300000000, which finally is linked to 2222444400000000. If _g_e_t_t_y is called without a second argument, then the first entry of /_e_t_c/_g_e_t_t_y_d_e_f_s is used, thus making the first entry of /_e_t_c/_g_e_t_t_y_d_e_f_s the default entry. It is also used if _g_e_t_t_y can not find the specified _l_a_b_e_l. If /_e_t_c/_g_e_t_t_y_d_e_f_s itself is missing, there is one entry built into _g_e_t_t_y that brings up a terminal at 333300000000 baud. It is strongly recommended that after making or modifying /_e_t_c/_g_e_t_t_y_d_e_f_s, it be run through _g_e_t_t_y with the check option to be sure there are no errors. FFFFIIIILLLLEEEESSSS /etc/gettydefs SSSSEEEEEEEE AAAALLLLSSSSOOOO getty(1M), login(1), stty(1), ioctl(2), termio(7). WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS To support terminals that pass 8 bits to the system (see the BBBBUUUUGGGGSSSS section), modify the entries in the /_e_t_c/_g_e_t_t_y_d_e_f_s file for those terminals as follows: add CCCCSSSS8888 to _i_n_i_t_i_a_l-_f_l_a_g_s and replace all occurrences of SSSSAAAANNNNEEEE with the values: BBBBRRRRKKKKIIIINNNNTTTT IIIIGGGGNNNNPPPPAAAARRRR IIIICCCCRRRRNNNNLLLL IIIIXXXXOOOONNNN OOOOPPPPOOOOSSSSTTTT OOOONNNNLLLLCCCCRRRR CCCCSSSS8888 IIIISSSSIIIIGGGG IIIICCCCAAAANNNNOOOONNNN EEEECCCCHHHHOOOO EEEECCCCHHHHOOOOKKKK. An example of changing an entry in /_e_t_c/_g_e_t_t_y_d_e_f_s is illustrated below. All the information for an entry must be on one line in the file. Original entry: CONSOLE # B9600 HUPCL OPOST ONLCR # B9600 SANE IXANY TAB3 HUPCL # $HOSTNAME console Login: # console Modified entry: CONSOLE # B9600 CS8 HUPCL OPOST ONLCR # B9600 BRKINT IGNPAR ICRNL IXON OPOST ONLCR CS8 ISIG ICANON ECHO ECHOK IXANY TAB3 HUPCL # $HOSTNAME console Login: # console This change permits terminals to pass 8 bits to the system so long as the system is in MULTI-USER state. When the system changes to SINGLE-USER state, the _g_e_t_t_y is killed and the terminal attributes are lost. So to PPPPaaaaggggeeee 2222 ggggeeeettttttttyyyyddddeeeeffffssss((((4444)))) ggggeeeettttttttyyyyddddeeeeffffssss((((4444)))) permit a terminal to pass 8 bits to the system in SINGLE-USER state, after you are in SINGLE-USER state, type (see _s_t_t_y(1)): _ssss_tttt_tttt_yyyy _----_iiii_ssss_tttt_rrrr_iiii_pppp _cccc_ssss_8888 BBBBUUUUGGGGSSSS 8-bit with parity mode is not supported. PPPPaaaaggggeeee 3333 
